FRVT 1:N Identification

Latest Report | Participation Agreement | API | Validation | Encryption

Status

[last updated: December 14, 2020]

A new FRVT 1:N report has been published. Prior editions of the 1:N report are here.

Updates have been made to the General Evaluation Specifications document and our validation package to reflect the update to CentOS 8.2 as the new evaluation operating system. From September 12, 2020 onward, we will require all algorithms submitted to any track of FRVT be compiled for the CentOS 8.2 operating system. Our image of that OS is available for download.


FRVT Participation Statistics

[last updated: January 27, 2021]

2018 2019 2020 2021 Total
Number of algorithms 209 31 23 5 268
Number of unique developers 53 25 20 5 70

Performance

[last updated: December 14, 2020]

Identification Performance

Identification Performance

The table below shows False Negative Identification Rates (FNIR) for the case where a threshold is set to limit to the False Positive Identification Rate (FPIR) to 0.003. FNIR is the proportion of mated searches failing to return the mate above threshold. FPIR is the proportion of non-mated searches producing one or more candidates above threshold. The threshold is set for each algorithm and each column separately. The use of thresholding supports use of face recognition in making mostly automated decisions e.g. for access into facility. The first row in the header shows the type of image enrolled in the gallery; the second row shows the search image type; the third row shows the number of persons in the gallery. The images are described in the section 2 of the report. In all cases, each person is enrolled with one image only.

Investigation Performance

Investigation Performance

The table below shows False Negative Identification Rates (FNIR) for the case where the threshold is set to zero and the algorithm returns a fixed number (50) of candidates. FNIR is the proportion of mated searches for which the algorithm does not place the correct candidate at rank 1. The use of face recognition without a threshold supports investigate uses where it is assumed and necessary that a human will be used to review the candidates returned from each search. For mated-searches the human is tasked with finding the correct mate; for non-mated searches the reviewer must reject all the candidates. The first row in the header shows the type of image enrolled in the gallery; the second row shows the search image type; the third row shows the number of persons in the gallery. In all cases, each person is enrolled with one image only.

Resources Performance

Resources Performance

PLACE HOLDER TEXT HERE

Prior Editions of Report

All prior Ongoing FRVT 1:N reports can be accessed from here.

How to Participate

To participate in this evaluation, developers need to submit a participation agreement to NIST, wrap their software behind the published C++ API, run their libraries through the provided validation package (which creates a submission package), encrypt the package, and provide a download link for the encrypted submission package. More details are provided below.

Participation Agreement

A new Participation Agreement for the FRVT Ongoing 1:N track has been published. All organizations wishing to participate in the 1:N track must submit a new Participation Agreement to NIST by mail AND send a PDF scanned copy to frvt@nist.gov. [last update: 2021-01-13]

API Document

A new API document has been published. All FRVT APIs reference the supporting FRVT General Evaluation Specifications, which includes hardware and operating system environment, software requirements, reporting, and common data structures that support the APIs. Developers must ensure that their submission conforms to the API specifications. [last update: 2020-09-10]

Validation

An updated validation package has been published. All participants must run their software through the validation package prior to submission. The purpose of validation is to ensure consistent algorithm output between your execution and NIST’s execution. [last update: 2020-09-10]

Encryption

All submissions must be properly encrypted and signed before transmission to NIST. This must be done according to these instructions using the FRVT Ongoing public key linked from this page. Participants must email their public key to NIST. The participant’s public key must correspond to the participant’s public-key fingerprint provided on the signed Participation Application. [last update: 2017-11-20]

Submission

Encrypted files below 20MB can be emailed to NIST at frvt@nist.gov. Encrypted files above 20MB can be provided as a download link from a generic http webserver (e.g., Google Drive). We cannot accept Dropbox links. NIST will not register, or establish any kind of membership, on the provided website. Participants can submit their algorithm(s) as soon as the signed participation agreement is sent to NIST. There is no need to wait for NIST confirmation of the received agreement. Participants must subscribe to the FRVT mailing list to receive emails when new reports are published or announcements are made. [last update: 2017-11-20]

Contact Information

Inquiries and comments may be submitted to frvt@nist.gov.

Subscribe

Subscribe to the FRVT mailing list to receive emails when announcements or updates are made.

Related NIST Projects

FRVT Ongoing
FRVT 1:1 Verification
FRVT Demographic Effects
FRVT MORPH
FRVT Quality Assessment
FRVT Face Mask Effects